An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello to the community. I’m hoping someone here can help me. we have been developing our mobile app with a 3rd party contractor. I used to provide feedback through TestFlight screen shot program and it was great. Straight from my iPhone to the dev team. Screen shots with descriptions of the problem. they recently transferred the app to our account and I think since then we can no longer receive the feedback. in fact, last week I spent 2 hours reviewing the app. Sending tons of screen shot feedback with comments. Thinking they were receiving them. But nothing. when we log into our feedback portal I only see feedback from 70 days ago. And nothing from recent. I made sure that feedback is welcome ( see screen shot ) i tested individual feedback test and got nothing. here are my questions. Is there a way to recover that feedback. Where is it going ? How can I get this feature working properly again so I can effectively and efficiently review the app and provide feedback to the developers.

I'm building a custom keyboard extension that offers voice dictation. Because keyboard extensions are constrained (memory cap ~30–48 MB, restricted audio session access), I delegate recording to my container app: User in a host app (e.g., Safari) taps the mic in my keyboard extension. The keyboard calls extensionContext.open(URL("myapp://dictation")) to launch the container app. The container app records audio via AVAudioEngine + SFSpeechRecognizer, writes the final transcript to the App Group, and signals completion via a Darwin notification. 4. The user is expected to be returned to the original host app (Safari) automatically so they can keep typing. The problem (step 4): On iOS 26.4 I can no longer identify which app was the host. Every previously-known path returns nil for the keyboard extension's host: parent.value(forKey: "_hostBundleID") → returns the literal string parent.value(forKey: "_hostApplicationBundleIdentifier") → returns NSNull xpc_connection_copy_bundle_id on the underlying XPC connection (via PKService.defaultService.personalities[…]) → returns NULL NSXPCConnection.processBundleIdentifier on extensionContext._extensionHostProxy._connection → returns nil proc_pidpath(hostPID, …) → EPERM from the keyboard sandbox LSApplicationWorkspace.frontmostApplication → selector unavailable from the extension RBSProcessHandle.handleForIdentifier:error: → returns an RBSServiceErrorDomain error Without the host's bundle ID, the container app has no way to call LSApplicationWorkspace.openApplicationWithBundleID: (the technique that worked on iOS 25 and earlier). UIApplication.suspend() correctly sends the container to background, but iOS treats us as a "fresh launch" — it returns the user to the Home Screen instead of Safari, because the container app was launched by an extension, not directly by Safari. KeyboardKit's maintainer reached the same conclusion (issue #1014) and shipped 10.4 without the feature. My questions: Is there a public, App-Store-safe API in iOS 26+ for a custom keyboard extension to identify its host application, or for the container app (launched via the extension's openURL) to identify which app initially hosted the extension that opened it? UIOpenURLContext.options.sourceApplication reports the extension's own container, not the actual host. 2. Is there a public mechanism for "return to source app" when the container app was launched by an extension's openURL? Equivalent to the ← Source affordance iOS shows for normal inter-app openURL, but triggered programmatically by the launched app. 3. Some popular keyboards (e.g., 微信输入法 / WeChat Keyboard) still appear to round-trip through their container app on iOS 26.4 and return the user to the original host — including the iOS ← WeChat back affordance in the host's status bar afterward. What's the recommended approach to achieve this? If it requires a specific scene-activation flow, NSUserActivity pattern, or extension-context configuration, please point at the relevant docs. 4. If there is no public path today, is FB22247647 (or a related radar) the right place to track this? Should developers in this position migrate to in-extension audio capture (which has its own significant constraints in keyboard extensions)? I'd much rather not rely on private APIs. Concrete guidance — or even an acknowledgment of which direction Apple intends — would help thousands of custom-keyboard developers who currently have a degraded voice-input experience on iOS 26.4+. Tested on iPhone 12 Pro Max running iOS 26.4.2 (build 23E261), Xcode 26.x, Swift 5. Thanks!

Hello, Our iOS app’s TestFlight external testing build has been stuck in “Waiting for Review” for several days. This is for TestFlight External Testing, not an App Store public release submission. We have already provided the Beta App Review Information, including review notes, test instructions, contact information, and a working demo account. Current situation: App name: Linic Platform: iOS Submission type: TestFlight External Testing Status: Waiting for Review Submitted date: June 4 ~ June 5, 2026 Build number: 1.4.2(8)、1.4.3(9) Bundle ID: com.lincept.linny Beta App Review Information: already updated Demo account: provided in App Store Connect We would like to understand whether this is currently expected queue behavior, whether TestFlight external beta reviews are experiencing delays, or whether there is any additional information we should provide to help the review proceed. Has anyone recently experienced a similar delay with TestFlight External Testing builds stuck in “Waiting for Review”? If so, did contacting Apple Developer Support or submitting an expedited review request help? Thank you.

Is anyone else experiencing unusually long App Review times? My app has been in review for about a month now with no progress. After waiting for so long, I cancelled and resubmitted it twice, hoping it might help, but the situation remains exactly the same. I've also contacted App Review and submitted a request for an update, but I haven't received any response yet. At this point, I'm wondering if anyone else has gone through something similar recently. How long did it take to get resolved, and is there anything else I can do besides continuing to wait?

Hi Apple Team, We're looking for guidance from developers who have successfully resolved a rejection under App Review Guideline 3.2.1(viii). Our app is mPokket: Instant Loan App, a consumer lending application that has been live on Google Play for nearly 10 years. The app is published by Maybright Ventures Private Limited, which owns and operates the mPokket lending business and brand. While consumers know the service as "mPokket," the legal entity behind the business and the developer account is Maybright Ventures Private Limited. Our iOS app has now been rejected twice with the following message: "The app provides loan services but the domains listed on the app's Product Pages are not clearly under your control or ownership." Apple also mentions that the Product Page domains and the email domains of the Apple Accounts associated with the developer account should clearly identify the company providing the loan services. Has anyone faced a similar situation where: The consumer brand name is different from the parent/legal entity name? The developer account is under the parent company while the app is marketed under a consumer brand? App Review requested additional clarification regarding ownership of the lending business and website domains? If so, what documentation or changes helped obtain approval? Did you need to: Change the Account Holder/Admin Apple IDs to use the parent company's domain? Add additional ownership documentation? Provide a corporate structure explanation or trademark/brand ownership details? Any guidance or experience would be greatly appreciated. Thank you.

Hello, I'm hoping someone from the App Review team can look into this situation, which has specific context that I believe makes it worth a careful look. Thank you in advance for your time. I'm hoping someone from the App Review team can look into this situation, which I believe has specific context that makes it worth a careful look. My app YADA: You've Already Met (App ID: 6759586097) has been in "Waiting for Review" since Wednesday May 6 at 7:44 PM ET - now over 96 hours. I have an open support case (20000112508151) filed Friday with no response yet. I'm not writing simply to flag the wait - I want to explain why this submission deserves a thoughtful second look on the merits. When YADA was submitted for TestFlight beta review, it was flagged under Guideline 4.3(b) for the same reason as the App Store rejection. I appealed, explained the differentiating mechanic, and an Apple reviewer evaluated the argument and approved the app for external testing. That approval is on record. I'm asking for consistency with that prior decision. YADA's core mechanic is genuinely unlike any dating app currently on the App Store. A user privately adds someone they already know to a list. That person receives no information about who added them. A match is only revealed when both people have independently and privately added each other. If the feeling isn't mutual, nothing is ever disclosed. There is no browsing of strangers, no algorithmic recommendations, no swiping, and no rejection possible because neither party knows they've been added until both have added each other simultaneously. Critically, YADA does not ask users to declare their gender or sexual preferences - because the mechanic doesn't require it. This makes YADA the only interest-discovery platform on the App Store that works entirely without those declarations, which creates a uniquely safe experience for LGBTQ+ users and young people who are not ready to publicly disclose their orientation. No equivalent experience exists on the App Store. The App Store rejection also included 5.1.1 and 2.1 issues, both of which I fully resolved - redesigning the contacts permission flow with a proper in-app explanation screen and directly answering Apple's question about data handling - with a new build submitted alongside my Resolution Center reply. I'm not asking for special treatment. I'm asking for the opportunity to have the full argument evaluated by a reviewer with the time to consider it, consistent with how the TestFlight review was handled. Support case: 20000112508151. App ID: 6759586097. Submission ID: abdf8b5b-5ea0-46a4-8a0b-fb58320fa701. Thank You

I’m working on an iOS app and need help with ASO to find the best keywords for title, subtitle, description, and keyword field. Can anyone suggest free tools that show keyword volume, difficulty, and competitor keywords?

Hello! I can't stand the problem with Apple anymore and I don't know what to do. I get an update every few days to the application, I send it back for review, but every 4-5 days I get a rejection again. I don't know how to communicate directly with them and have them tell me the problem clearly, not just 5.2.2 I need transparent and fast communication. I've already lost a lot of time and money, I have other projects pending and I don't know what to do in this situation. I'm waiting for some advice and maybe a direct contact with the Apple developer. Thank you! Apple ID: 6770487788 Other App: 6770216468

Hi, I can sign in to my Apple ID, but my Apple Developer account shows a “closed” status and I’m unable to access App Store Connect features. My app is currently showing “Ready for Distribution,” so the account appears active, but developer access is restricted. I’ve already contacted Apple Developer Support and am waiting for their response. Also, I temporarily can’t access my primary email due to a verification issue, so I’ve provided an alternate contact email and phone number in my support request. Has anyone experienced a similar situation or knows possible reasons for a “closed” developer status while the app remains approved? Thanks.

Hello everyone, I submitted the first update for my app on April 14. On April 18, I canceled that submission and immediately resubmitted it the same day, as many people suggested that resubmitting might help speed up the review process. Today is June 4, and after 47 days, the update is still stuck in “Waiting for Review.” I’ve seen that many other developers are experiencing the same issue, but 47 days is a very long time for me, and I have no idea how much longer I should expect to wait. I hope we can all find a solution to this situation soon. Any advice, insights, or shared experiences would be greatly appreciated. Thank you all.

Body We are currently evaluating an architecture approach for an iOS application and are looking for guidance on App Store Review expectations and platform limitations. Context We are modernizing an existing healthcare application that handles regulated data (PHI). The application is intended for use by internal staff and authorized third-party contractors (not a consumer-facing app, and no monetization). To support iOS distribution, we are evaluating packaging an Angular-based Progressive Web App (PWA) using a lightweight native wrapper (e.g., via PWABuilder), resulting in a WebView-hosted application. Proposed Architecture Angular PWA hosted remotely and loaded via HTTPS Packaged inside a native iOS container (WKWebView-based) Authentication via Passkeys (WebAuthn / FIDO2) Backend APIs implemented in .NET Limited offline functionality using IndexedDB (non-sensitive data only) No persistent storage of sensitive data on-device The native wrapper primarily provides distribution and lifecycle management; most functionality is delivered via the hosted PWA. Key Consideration This application is not intended to function as a general-purpose browser, but rather as a purpose-built, workflow-specific experience for healthcare operations. Questions 1. App Review / Guideline 4.2 Have developers had success getting WebView-hosted applications (primarily PWA-driven) approved when they provide a complete and production-grade user experience? How does Apple typically evaluate whether such an app meets the “minimum functionality” requirement versus being considered a repackaged website? 2. Dynamic Content / Updates Are there specific restrictions on delivering functionality dynamically via server-hosted content after app approval? At what point would backend-driven changes require a new App Store submission? 3. Data Storage & WebView Behavior Are there notable differences in how iOS handles storage (e.g., IndexedDB, local storage) in: Safari-installed PWAs WebView-based apps distributed via the App Store? Are there known limitations or caveats when relying on IndexedDB within WKWebView? 4. Platform Capabilities Are there practical limitations for WebView-based apps related to: Offline functionality File handling Long-term platform support 5. Healthcare / Regulated Data For apps handling regulated healthcare data (PHI), are there additional expectations or best practices (beyond standard guidelines) that Apple reviewers typically look for? Goal We are trying to determine whether this architecture is viable for App Store distribution before proceeding further with implementation. Any insights, experiences, or pointers to relevant documentation would be greatly appreciated.

Hi everyone, I’m trying to fix an App Review rejection related to auto‑renewable subscriptions, and I’m also blocked because my subscriptions don’t work in the sandbox even though configuration looks correct. App Review details App version: 3.5.3 Review device: iPhone 17 Pro Max iOS: 26.4 Guidelines: 3.1.2(c) and 2.1(b) Reviewer message says: Missing required subscription metadata links: Terms of Use (EULA) link in App Description (or custom EULA set in App Store Connect) Privacy Policy link in the Privacy Policy field in App Store Connect IAP bug / error during purchase (sandbox testing during review) What I see in App Store Connect My subscription products show “Developer Action Needed”. Subscription group/products are created (monthly + yearly). I believe all required subscription info is filled out (pricing, localization, etc.), but sandbox purchases still fail. Sandbox behavior / issue In Sandbox on device, attempting to purchase or load products results in an error on IAP (reviewer didn’t provide the exact error text). I’m using StoreKit (happy to share whether it’s StoreKit 1 vs StoreKit 2 if that matters) and fetching products by product IDs. Additional blocker: Banking info stuck “Processing” In App Store Connect → Agreements, Tax, and Banking, my banking section shows: “Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then.” But the banking status has stayed Processing for more than 2 weeks and never changes. I don’t know how to resolve this, and I suspect it might be related to why subscriptions are failing in sandbox / showing “Developer Action Needed”. Questions: What are the most common reasons subscriptions show “Developer Action Needed” and are rejected/blocked even when the setup seems complete? For Guideline 3.1.2(c): what is the correct place/best practice to provide the required links? Put Apple Standard EULA link in App Description? Add custom EULA in App Store Connect → App Information → EULA? Add Privacy Policy URL in App Store Connect Privacy Policy field (or the dedicated Privacy Policy URL field)? For the sandbox IAP error during review: Could this be caused by agreements / banking stuck in Processing or Paid Apps Agreement not active/accepted (even though the app is free but uses subscriptions)? Can “Developer Action Needed” prevent sandbox transactions from working for reviewers and my tests? Any recommended step-by-step checklist to validate subscriptions end-to-end (agreements, banking/tax, subscription metadata, product status, storefront, etc.)? Has anyone seen banking updates stuck in Processing for weeks? What is the best way to resolve it (waiting, re-submitting banking info, contacting Apple, specific support channel)?

Hello App Review Team, Our app submission has been stuck in the “Waiting for Review” status for an extended period, and we would like to kindly ask whether there is any issue or additional action required from our side. We have already uploaded the latest build and verified the In-App Purchase configuration in App Store Connect. Since the status has not changed, we wanted to check if the submission queue is functioning normally or if there is anything preventing the review from starting. We would appreciate any clarification or guidance you can provide. Submission ID: 85a6b879-5218-4f2c-b444-de09d148268e Apple ID: 6766198981 Best regards, Mert Akgün

Hello, I’m posting again because our previous forum post received the following Apple Staff reply: “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, the issue has not been resolved yet. We have not received any separate contact in App Store Connect, the Resolution Center, or email. We currently have two active apps in the same developer account that are stuck in Waiting for Review. Because multiple apps in the same account are affected at the same time, this seems like it may be an account-level App Review queue or routing issue rather than an individual app binary issue. For one of the affected apps: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 Submitted: June 1, 2026 Review submission state: WAITING_FOR_REVIEW Review submission item state: READY_FOR_REVIEW App Store version state: WAITING_FOR_REVIEW Build processing state: VALID Build audience type: APP_STORE_ELIGIBLE Build expired: false TestFlight installation works normally, and there is no Resolution Center message. We are also unable to submit an expedited review request because the expedited review form itself fails. After selecting the correct app and platform, the form sends a POST request and receives HTTP 200 OK, but the response page displays: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” The POST payload includes the correct app ID and platform: expedite_app_id_req: 6760743106 expedite_app_platform: ios Could Apple Staff please check whether our developer account or these submissions are affected by an internal App Review queue/routing issue? We are currently blocked because the review has not started for multiple apps, we have not received any follow-up contact, and the expedited review request form cannot be submitted.

Hello Apple Staff, Thank you for your previous reply. After my initial post, I understood that my app would enter the review process shortly. However, another three days have passed, and the status of my app remains “Waiting for Review.” I am becoming increasingly concerned about whether my app has successfully entered the review queue. Prior to this, I have already tried the following support channels without success: Contacting Apple support by phone Reaching out via email Requesting an expedited review Posting on developer forums I fully understand that app review times may vary, and I truly respect the work of the App Review team. However, this situation is becoming more serious for us. This submission is critical for our users, and the ongoing delay is having a significant impact on our operations and business. App Details: App ID: 6764726742 Submit time: 2026-06-01 Submission ID: 187011d0-1390-4abe-9252-f13410307c31 Current Status: Waiting for Review I would greatly appreciate it if Apple could kindly verify the following: Whether the current submission is properly queued for App Review Whether there is any internal processing or queuing issue preventing the review from starting Whether any action is required from my side that is not visible in App Store Connect If possible, could an Apple staff member please escalate this case to the App Review team, or at least confirm that the submission is correctly queued? I would be extremely grateful for any help or clarification. We feel stuck because we have tried every available support channel, yet the app remains in “Waiting for Review” with no progress. Thank you very much for your time and support. Best regards, Leon

Hello, I’m posting again because our previous forum post received the following Apple Staff reply: “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, the issue has not been resolved yet. We have not received any separate contact in App Store Connect, the Resolution Center, or email. We currently have two active apps in the same developer account that are stuck in Waiting for Review. Because multiple apps in the same account are affected at the same time, this seems like it may be an account-level App Review queue or routing issue rather than an individual app binary issue. For one of the affected apps: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 Submitted: June 1, 2026 Review submission state: WAITING_FOR_REVIEW Review submission item state: READY_FOR_REVIEW App Store version state: WAITING_FOR_REVIEW Build processing state: VALID Build audience type: APP_STORE_ELIGIBLE Build expired: false TestFlight installation works normally, and there is no Resolution Center message. We are also unable to submit an expedited review request because the expedited review form itself fails. After selecting the correct app and platform, the form sends a POST request and receives HTTP 200 OK, but the response page displays: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” The POST payload includes the correct app ID and platform: expedite_app_id_req: 6760743106 expedite_app_platform: ios Could Apple Staff please check whether our developer account or these submissions are affected by an internal App Review queue/routing issue? We are currently blocked because the review has not started for multiple apps, we have not received any follow-up contact, and the expedited review request form cannot be submitted.

Hello, I received a Pending Termination Notice for my Apple Developer Program account. I submitted my first appeal on May 19, 2026. After receiving no response for an extended period, I submitted a second appeal with additional clarification and information. Most recently, I opened an Apple Developer Program Support case on June 2, 2026. I received the automatic confirmation email and case ID, but I have not received any further communication. At this time: My App Store Connect account remains accessible. I have not received a final decision. I have not received any request for additional information. I have not received any update regarding the status of the review. I understand that account reviews may take time, but I am unsure whether this length of silence is normal for a Pending Termination Notice case. Has anyone experienced a similar situation? Is there any recommended way to follow up, or should I simply continue waiting for a response from Apple? Thank you for any guidance.

I'm hoping someone here has been through a similar situation and can help. Our app was rejected under Guideline 4.3 (Design Spam), but I believe this is a misunderstanding. This app was previously approved under a different developer account — we had to resubmit under a new account due to an internal business restructuring. The app itself has not changed at all. Here's the timeline: May 24 — Filed an appeal May 26 — Filed another appeal Jun 4 — Filed another appeal Jun 7 (today) — Filed yet another appeal It has now been over 2 weeks since the first appeal with no response whatsoever. This is genuinely just a resubmission of an already-approved app due to a company account change — not an attempt to game the review process in any way. The situation is urgent as we have a launch scheduled for this week. Every day of delay is directly affecting our users and timeline. Has anyone experienced this? How did you get it resolved? Is there any way to escalate beyond the Resolution Center? Any advice would be truly appreciated.

Hello, Our iOS app’s TestFlight external testing build has been stuck in “Waiting for Review” for several days. This is for TestFlight External Testing, not an App Store public release submission. We have already provided the Beta App Review Information, including review notes, test instructions, contact information, and a working demo account. Current situation: App name: Linic Platform: iOS Submission type: TestFlight External Testing Status: Waiting for Review Submitted date: June 4 ~ June 5, 2026 Build number: 1.4.2(8)、1.4.3(9) Bundle ID: com.lincept.linny Beta App Review Information: already updated Demo account: provided in App Store Connect We would like to understand whether this is currently expected queue behavior, whether TestFlight external beta reviews are experiencing delays, or whether there is any additional information we should provide to help the review proceed. Has anyone recently experienced a similar delay with TestFlight External Testing builds stuck in “Waiting for Review”? If so, did contacting Apple Developer Support or submitting an expedited review request help? Thank you.

I have submitted my app since the last 3 weeks, until now it is still "Waiting for review" I also did not receive any errors or notifications saying why its stuck. Can someone help me?